BackNode Upgrade

Node Upgrade

Liquid Networ
2026-09-09 14:45:51

Liquid releases emergency Elements v23.3.4 update to fix proof verification cache flaw

Liquid Network said on Sept. 9 that it has released an emergency Elements v23.3.4 update and urged all Liquid node operators to upgrade, as functional nodes were already moving to the new version. The release fixes a proof verification cache vulnerability by strengthening the cache key used for range proofs, according to the network’s notice. Liquid added that the patch has gone through multiple rounds of internal and external review involving teams including Bitcoin Red Team and Alpen Labs. The network also outlined an initial recovery plan. It intends to resume block production first while peg operations remain paused, then replay transactions that have already been verified as valid, and only restore peg operations after the network is fully recovered and funds have been returned. Blockstream is testing the first two phases in parallel, and said the order and implementation details could change depending on test results. Liquid also warned that scammers have set up fake update websites and told users to rely only on official Liquid Network and Blockstream channels, and not to send funds to unknown parties or reveal private keys or seed phrases.

640
Liquid releases emergency Elements v23.3.4 update to fix proof verification cache flaw
Polygon
2026-08-29 11:26:53

Polygon Labs Urges Node Upgrade After Austin and Kyoto Hard Forks; Old Bor/Heimdall Clients Out of Consensus

Polygon Labs has issued an urgent notice after the Austin and Kyoto hard forks went live on the Polygon PoS network, warning that nodes still running outdated Bor or Heimdall clients have fallen out of consensus. According to CryptoSlate, the Austin fork activated at mainnet block 91,949,700 and requires Bor v2.1.0 or later, while the Kyoto fork activated at height 51,533,000 and requires Heimdall v0.11.0 or later. Austin addresses two Bor resource-exhaustion issues: one where L1-to-L2 bridge state sync events were not counted toward the Gas limit, which could slow block processing, and another where the TxDependency field had no size limit, potentially allowing peer nodes to be crashed. Kyoto patches a set of vulnerabilities, including deeply nested message attacks, fee coin scanning, and checkpoint signature recovery. Both hard forks are described as pure binary upgrades, meaning no state migration is required and nodes that have not forked do not need to resync. Polygon Labs urges operators of older clients to upgrade promptly and, if necessary, resume synchronization under its guidance.

740
Polygon Labs Urges Node Upgrade After Austin and Kyoto Hard Forks; Old Bor/Heimdall Clients Out of Consensus
TRON
2026-07-22 07:40:00

TRON rolls out GreatVoyage v4.8.2 and sets a mandatory node upgrade deadline

TRON has officially released GreatVoyage-v4.8.2, also known as Pyrrho, according to ChainCatcher. The update adds deeper compatibility with Ethereum’s Pectra and Osaka upgrades and introduces several technical changes, including the CLZ instruction and a secp256r1 signature verification precompile. It also replaces fastjson with Jackson and moves node monitoring metrics from InfluxDB to Prometheus. The release is mandatory for node operators. TRON said operators must complete the upgrade by 23:59 Singapore time on Aug. 16, 2026, or risk affecting block synchronization. The network’s Event Plugin has also been upgraded to v3.0. Nodes using the official plugin are required to upgrade the plugin first before updating the node version, while operators running self-developed plugins are advised to complete compatibility work as soon as possible. TRON said the release strengthens the network’s capabilities in smart contract compatibility, interface handling, node monitoring, and operations management.

1190
TRON rolls out GreatVoyage v4.8.2 and sets a mandatory node upgrade deadline